IMPORTANT: Make sure that your system meets the minimum requirements as indicated in the System Requirements section in the inPilot Overview chapter of this guide.
WARNING: Failure to configure these settings may cause data loss and will minimally cause errors in the operation.Prior to installing the inPilot components onto the server hardware, there are numerous system environment configuration settings that should be configured. While PostgreSQL will be installed during the installation procedure, these settings must be configured manually.
Add the following values to system file in the /etc/system directory if they are not present and restart the system before continuing with the installation of the inPilot components.
set msgsys:msginfo_msgmnb=65536
set msgsys:msginfo_msgtql=1024
set shmsys:shminfo_shmmax=1300000000
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=256
set shmsys:shminfo_shmseg=256
set semsys:seminfo_semmap=256
set semsys:seminfo_semmni=512
set semsys:seminfo_semmns=512
set semsys:seminfo_semmsl=270
set msgsys:msginfo_msgtql=1024
set shmsys:shminfo_shmmax=1300000000
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=256
set shmsys:shminfo_shmseg=256
set semsys:seminfo_semmap=256
set semsys:seminfo_semmni=512
set semsys:seminfo_semmns=512
set semsys:seminfo_semmsl=270
|
1
|
The recommended filesystem for installation is ZFS. If installation is performed on any other filesystem, a warning message appears indicating the recommended filesystem.
|
|
2
|
inPilot must be installed as a root user on the system. Installation with other user privileges is not recommended.
|
|
3
|
Make sure no other Apache web server is running on the port being used for installation (default port is 8080). If it is, stop it before proceeding with the installation or provide a different port for Apache server. Check if an application is running on a given port by entering the following command:
|
|
4
|
Make sure no other Postgres server is running on the port being used for installation (default port is 5432). If it is, stop it before proceeding with the installation or provide a different port for Postgres server. Check if an application is running on a given port by entering the following command:
|
|
5
|
Make sure no other server is running on the port being used for installation for XML-RPC (default port is 9999). If it is, stop it before proceeding with the installation or provide a different port for XML-RPC server. Check if an application is running on a given port by entering the following command:
|
The inPilot installation files are distributed as a single compressed file with a .tar.gz extension.
IMPORTANT: The inPilot application supports both Solaris-Sparc and Solaris-x86 platforms. The installable tar file names help in identifying the platform. For example, starbi_x.x.x_sparc.tar.gz indicates that this file is for Solaris-Sparc platform. starbi_x.x.x_x86.tar.gz indicates that this file is for Solaris-x86 platform.For information on downloading the appropriate inPilot package for your requirements, contact your sales representative.
Once the installation file has been copied to the server, use the following procedure to install the inPilot application.
gunzip starbi_x.x.x_x.tar.gz
tar -xvf starbi_x.x.x_x.tar
|
l
|
README: A text file containing information pertaining to the release.
|
|
l
|
install_starbi: A script to install the inPilot application.
|
|
l
|
starbi.tar: A compressed file containing all the application files required for inPilot installation.
|
|
l
|
uninstall_starbi: A script to uninstall the inPilot application.
|
|
l
|
uninst: A GUI/Console based uninstaller to uninstall the inPilot application.
|
|
l
|
inst: A GUI/Console based installer to install the inPilot application.
|
|
l
|
In_Pilot_Installer.bin: The executable used by inst to install inPilot application.
|
|
5
|
Respond to the on-screen prompts with the help of inputs given in the following table and configure various parameters as required.
|
IMPORTANT: The installation script checks the disk space in the system. If the available disk space is lesser, then the script will give an error and abort the installation process.After you have provided the inputs, the installation script starts the inPilot components and you receive a message indicating that inPilot installation is completed.
gunzip starbi_x.x.x_x.tar.gz
tar -xvf starbi_x.x.x_x.tar
|
l
|
README: A text file containing information pertaining to the release.
|
|
l
|
install_starbi: A script to install the inPilot application.
|
|
l
|
starbi.tar: A compressed file containing all the application files required for inPilot installation.
|
|
l
|
uninstall_starbi: A script to uninstall the inPilot application.
|
|
l
|
uninst: A GUI/Console based uninstaller to uninstall the inPilot application.
|
|
l
|
inst: A GUI/Console based installer to install the inPilot application.
|
|
l
|
In_Pilot_Installer.bin: The executable used by inst to install inPilot application.
|
./inst [MODE]
|
l
|
|
l
|
The command ‘inst/uninst -help' provides usage of the scripts. This script installs the Apache, Postgres and Scheduling servers functionality. The display must be set for running in GUI mode, else the installation will run in Console mode.
|
5
|
Click Next to proceed.
|
|
6
|
Respond to the on-screen prompts with the help of inputs given in the following table and configure various parameters as required.
|
|
This dialog asks the user to check the variable values in ‘/etc/system’ file. If one or more entries are missing, click Cancel button to update ‘/etc/system’ and restart the system to re-run installer.
|
||
|
Select Browse button to change the installation path.
|
||
|
Administrator password
|
||
|
Enter data directory path
|
Select Browse button to change the installation path.
|
<inpilot_install_dir>/starbi/postgres/data
|
|
Type the port number over which Apache web server communication will occur with inPilot.
Ensure that no other Apache web server is running on the port being used for installation. If the port is being used, abort the installation.
|
||
|
Type the port number over which XML-RPC server communication will occur with inPilot.
|
||
|
Enter archive directory path
|
Select Browse button to change the installation path.
|
<inpilot_install_dir>/archive
|
|
inPilot Bulkstat File Transfer Interval [secs]
|
||
|
inPilot Bulkstat Sample Interval [secs]
|
||
|
The pre-installation screen displays the product name, install location, other product configurations, and disk space information before installing the product.
|
||
|
Click Cancel button to stop installation.
|
||
|
Start All Servers After Installation
|
Click Next to proceed.
|
|
|
Click Done button to quit the installer.
|
||
Verify that the inPilot application is running and accessible by entering the following URL in your Web browser:
http://<inpilot_installation server name or IP address>:<apache port>
For information on using the inPilot GUI, see the inPilot Online Help documentation.
The upgrade procedure ensures that the data in the database is retained in the new installation. It also ensures that if there are any pending files to be processed in the old installation, then those file are also made available in the new installation.
CAUTION: Please contact your local support representative to ensure compatibility prior to upgrading.ls -lrt <install path>/starbi/data/temp_data_files/<img name>/edr/normalized_data/data
ls -lrt <install path>/starbi/data/temp_data_files/<img name>/edr/normalized_http_data/data
Check if the above commands return any pending input EDR files for the available gateways. If yes, wait for some time (5-10 minutes) to let the inPilot process finish these pending EDR files. Check again, and repeat the procedure until there are no pending EDR files for the available gateways. [This is to make sure that you do not not stop any inPilot process while processing.]
|
2
|
Stop the inPilot application using the following command from the <inpilot_install_dir>/starbi/bin directory:
|
In case of the first two upgrade options mentioned above, make sure that you are enter the old installation path (<install_dir>) for upgrade when prompted for the 'inPilot Installation directory'. In case of the third upgrade option, it automatically detects the old installation path through registry information.The installation automatically detects earlier setup and reads required configuration for Apache, Postgres and RPC port, etc. You will be prompted with a confirmation message before proceeding with the upgrade process.
After upgrade, the log files are generated at /starbi/logs/ directory.
WARNING: It is recommended that you manually perform a backup of all critical and historical data files before proceeding with this procedure. Failure to do this causes removal of all the directories, files and database.The inPilot application and its components can be uninstalled using one of the following two methods:
This method must be used if installation has been done using install_starbi script.
This method must be used if installation has been done using GUI/Console based installer (using inst).
Change to the directory in which inPilot is installed and execute the script by entering the following command:
./unins [MODE]
|
l
|
|
l
|
